BlueCielo Meridian Enterprise Server 2016 Administrator's Guide

Installing AutoVue

Installing AutoVue includes installing the AutoVue software on a Java application server and installing the components that integrate AutoVue on the web server and on the Java application server (if separate). The AutoVue software and documentation are available on the BlueCielo FTP server. Installation also includes configuring Enterprise Server to connect to those components when a document should be viewed.

Notes

• Each version of the AutoVue software supports specific Java versions as listed in the BlueCieloMeridian Enterprise Server Supported Software. If the computer on which you want to install AutoVue must use a Java version that is unsupported by AutoVue in order to support another application, you can configure separate Java versions on the same computer for each application as described in Deployment Rule Set.

• If AutoCAD drawings will be viewed that use custom font (.shx) files, place copies of the font files in the following location after installation:

  C:\Oracle\AutoVue\bin\fonts

• When the Meridian Enterprise Server server is upgraded to a new release, also upgrade the AutoVue server at the same time. The AutoVue server software must be the same version as the JVue applet that is included in the Meridian Enterprise release.
• If you install Meridian Enterprise on a server with the AutoVue Client/Server Integration component selected, then later install AutoVue, and still later repair the Meridian Enterprise installation, the AutoVue integration files might reside in the wrong folder. To resolve this issue, run the Meridian Enterprise setup program, select the Modify option, remove the AutoVue Client/Server Integration component , and then run the setup program again and reinstall it.
• If Meridian Enterprise and Meridian Explorer are used together in the same environment, they can share the same AutoVue deployment. The version of AutoVue that is supported by the Meridian Enterprise version should be used by both Meridian Enterprise and Meridian Explorer. The integration components for Meridian Enterprise are installed only by the Meridian Enterprise installation package and are specific to a particular AutoVue version. The .jar files that are installed with Meridian Explorer (by default, in C:\inetpub\wwwroot\<WebSite>\Jar\Res) should be replaced by the versions that are installed by Meridian Enterprise (by default, in C:\inetpub\wwwroot\AMM\Res).

• By default, client computers download documents to the Local Workspace when files are viewed. When configured to use AutoVue, this does not occur unless documents are printed from the viewer or if the viewer window is undocked from the primary client window.

  If the use of Local Workspace must be prevented completely, for example, to avoid installing SQL Server Compact Edition on the computer to manage the Local Workspace contents, then the vault must be configured to use the BlueCielo Filesystem Service (AMFS) instead. This can be done by disabling the Force clients to access documents from Local Workspace option (enabled by default) as described in the BlueCielo Meridian Enterprise Administrator's Guide. However, this will also negate the benefits of Local Workspace (also described in the BlueCielo Meridian Enterprise Administrator's Guide) and should be carefully considered.

• The user's preference settings are stored in files in the folder C:\Users\<UserName>\AppData\Roaming\Cyco\AutoManager View Control2.

The AutoVue software includes a copy of the open source Java application server software Jetty. This is convenient if you will be deploying AutoVue and do not have an existing Java application server on which to host AutoVue. It is also useful if you want a lightweight Java application server for desktop deployment. For convenience, the AutoVue installation packages install Jetty support by default.

The Jetty server is adequate for desktop deployments and small client/server deployments. In larger deployments, we recommend deploying the BlueCielo Connector component on the Apache Tomcat Java server instead. For guidance, refer to the BlueCielo knowledge base or BlueCielo ECM Solutions Technical Support.

The following instructions can also be used to install AutoVue as a desktop deployment. In that case, the references to different computers apply to the same computer.

Before you begin

• Microsoft .NET Framework 4.0 is required on the web server where the BlueCielo web service is installed in this task and ASP.NET must enabled.

  To enable ASP.NET, run one of the following from a command line window with elevated privileges, depending on the bit width and version of .NET Framework that is installed, and restart IIS:

  %windir%\Microsoft.NET\Framework\<VersionNumber>\aspnet_regiis.exe -i
  %windir%\Microsoft.NET\Framework64\<VersionNumber>\aspnet_regiis.exe -i
  

• Meridian Enterprise Server can use an existing AutoVue server that has already been configured to work with Meridian Enterprise as described in the BlueCielo Meridian Enterprise Administratorʹs Guide. Alternatively, another instance can be installed on a different server.
• Any firewall protecting the AutoVue server must allow inbound TCP traffic on port 80. Otherwise authentication or timeout errors can occur.

To install AutoVue:

1. Ensure that the server and client computers meet the hardware and software requirements described in the Oracle AutoVue Client/Server Deployment Installation and Configuration Guide and in the BlueCielo Meridian Enterprise Server Administrator’s Guide.

2. If an existing installation of AutoVue will be used, skip to the next step. Otherwise, perform this step.

   On the computer that will be the AutoVue server, install the AutoVue 2D or AutoVue 3D server software using its respective Oracle setup program. If both versions will be used, each version must be installed on its own computer. Use the instructions for non-integrated installation in the Oracle AutoVue Client/Server Deployment Installation and Configuration Guide. The following table lists the installation option responses that are adequate for integration with Meridian Enterprise Server.

   Oracle AutoVue installation options

   Option	Setting
   Specify Installation Directory	Accept the default (C:\Oracle\AutoVue)
   Select Install Set	Standard
   Select Shortcut Folder	Accept the default (Oracle AutoVue)
   Specify hostname or IP address for the AutoVue Server	Accept the default
   AutoVue Server Authentication	Configure Later
   Enabling SSL Communication	If you do not want to use the SSL protocol, select Configure Later. If you do want to use SSL: Select Configure SSL with a CA certificate and click Next. The Select the CA certificate file page appears. Select a valid CA certificate and click Next. The Select the Identity JKS Keystore file page appears. Click Next. A default file will be created as: C:\oracle\autovue\bin\AutoVueIdentity.jks The Specify the Identity JKS Keystore password page appears. Type a password and click Next. The password will be stored in the file: C:\oracle\autovue\bin\jetty\etc\jetty-ssl.xml Perform the rest of the steps described in Configuring viewing with SSL.

   Tip    These settings configure the AutoVue server as a stand-alone application that can be used outside of Enterprise Server by opening the page at http://<ServerName>/jVue/jVue.html.

3. On the AutoVue computer, run the Meridian Enterprise setup program that contains the same AutoVue version as the installed version of AutoVue and install the AutoVue Client/Server Integration component. This will add the BlueCielo Connector to AutoVue and install a BlueCielo web service in the IIS default website. If the Meridian Enterprise web server is a separate computer, run the setup program there also.

4. On the Meridian Enterprise web server, test the web service by opening it in a browser with the following URL.

   http://<ServerName>/BCWebService/BCWebService.BluePrintService.svc

   A page titled BluePrintService Service appears if installation is correct to this point.

5. On the AutoVue server, open the file StartServers.bat in any text editor and verify that the paths are correct for your installation. By default, it is located in C:\Oracle\AutoVue\bin.

6. By default, the Jetty application server, the AutoVue servlet, and the BlueCielo Connector servlet will be started automatically. If this fails due to system configuration or security issues, the server can be started manually by running StartServers.bat. Two command prompt windows and the AutoVue Server console window appear. If the last lines in the command prompt windows contain the text INFO: Started and the Processes boxes in the AutoVue Server window are green, the server started successfully. The windows must stay open but can be minimized. For more information about starting the servers automatically, see Starting the servers automatically.

7. On the 64-bit desktop client (not Web Access) computers, set the registry values that are described in the following tables. On the 32-bit desktop client computers, set the matching registry values in the Wow6432Node branch instead.

   Note    The values in the following settings are case-sensitive and must precisely match the folder and file names in your environment.

   HKEY_LOCAL_MACHINE\SOFTWARE\Cyco\AutoManager View Control2

   Value Name	Data Type	Value Data
   BluePrintWSDL	String	URL of the BlueCielo web service that you installed in step 3. For example: http://<ServerName>/BCWebService/BCWebService.BluePrintService.svc?wsdl
   DMSInfo	String	URL of the BlueCielo Connector that you installed in step 3. For example: http://<ServerName>:8900/wsclient/servlet/DMS. This setting should be the same as the BlueCielo Connector URL property of Meridian Enterprise Web Access.

   HKEY_CURRENT_USER\SOFTWARE\Cyco\AutoManager Meridian\CurrentVersion\Client\Settings

   Value Name	Data Type	Value Data
   ClientServerWebView	DWORD	If this value is 1, the client applications use the AutoVue viewer. If this value is 0, the client applications use the locally installed viewers.

   If you are installing AutoVue as a desktop deployment on one computer, also set the registry values that are described in the following table.

   HKEY_LOCAL_MACHINE\SOFTWARE\Cyco\AutoManager View Control2

   Value Name	Data Type	Value Data
   AppletRootPath	String	Path to the AutoVue Java applets, for example, C:\Oracle\AutoVue\bin\.
   AutoVueServer	String	URL to the AutoVue rendering server, for example, http://<ServerName>:5098/servlet/VueServlet. If the rendering server software is installed on the local computer, the location of the AutoVue configuration file, for example, direct//C:\Program Files (x86)\AutoVue\jVue20_0\bin\autovue.properties. The path settings in autovue.properties must be valid for the local computer.
   BCBeans	String	Path to the BlueCielo Java support libraries. By default, they are installed at: C:\Program Files (x86)\Common Files\Cyco Shared\AV\AMViewXBeans.jar.
   JAVAVMDLL	String	Path to the Java virtual machine DLL for support of AutoVue, for example, C:\Oracle\AutoVue\jre\bin\client\jvm.dll.

8. Check whether the AutoVue servlet is working:

   • Open a web browser window to the following URL:

     http://<ServerName>:5098/servlet/VueServlet

     A page titled VueServlet for AutoVue <Version> should appear.

9. Users must enable the AutoVue viewer before it will become their default viewer.

   • Web client users must enable the Use Oracle AutoVue for viewing documents option on the Preferences page in Web Access as described in theBlueCielo Meridian Enterprise Server Userʹs Guide.
   • Desktop client users must set the AutoVueViewer option first in viewer priority in the viewer options of Meridian Enterprise PowerUser as described in the BlueCielo Meridian Enterprise Userʹs Guide.
10. (Optional) Configure Meridian Enterprise Server to use the AutoVue server as described in Configuring the viewer options.

11. Test AutoVue by opening a document in the client application. The AutoVue applet downloads from the web server and opens the selected document.

    Notes    To prevent the Java authentication dialog from appearing at the beginning of each viewing session, you may need to configure one or more of the following settings:

    • Add the fully qualified name of the AutoVue server to the Local intranet zone in the Internet Explorer security options on the client computers but do not add it to the Trusted sites list.
    • Add the account name that is used for the application pool under which the web application is run (for example, Web Access or Meridian Explorer) to the Act as part of the operating system policy using the Local Group Policy Editor.
    • Define an authentication level for Network security: LAN Manager authentication level using the Local Group Policy Editor. The setting cannot be Not Defined.
    • On Windows Server 2003 and Windows XP computers, the account under which the BCConnectorService logs on should be changed from Local System to an account that has access to the website.

For more information about configuring and administering AutoVue, see:

• Oracle AutoVue Client/Server Deployment Installation and Configuration Guide
• Oracle AutoVue Desktop Deployment Installation and Configuration Guide